home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
3rdparty
/
nostop.nov
< prev
next >
Wrap
Text File
|
1994-01-16
|
4KB
|
88 lines
_________________________________________________________________
-----------------------------------------------------------------
THIS SECTION CONTAINS NOTICES AND TIPS SPECIFIC TO NOVELL SYSTEMS
_________________________________________________________________
-----------------------------------------------------------------
***NETWARE NETX.EXE BUG***
The February 1993 issue of BULLETS (a Novell publication for
developers) documents a bug in versions 3.26 and 3.31 of
NETX.EXE which may affect you. It has to do with a
failure to properly report an error when a file is accessed
which has been locked by another user. No*STOP NETWORK will
not make this problem worse, it will just mirror it.
_________________________________________________________________
-----------------------------------------------------------------
SETUP EXAMPLE FILES
The following Novell-specific files and scripts are used in our laboratory
when we test new versions. They are presented as examples for the new
user of No*STOP NETWORK.
*****************************************************************
SHELL.CFG
*****************************************************************
If you are a Novell user and are having a problem with No*STOP
NETWORK, the problem may lie within the SHELL.CFG file, or lack
thereof. The SHELL.CFG listed below is the one we use with ALL
Netware testing. It is by no means the only one that works, but
you may find some useful hints in it. Remember, the SHELL.CFG
must be in the same directory as IPX and NETx.
SEARCH MODE=1
NETBIOS INTERNET=OFF
FILE HANDLES=100
EOJ=ON
CACHE BUFFERS=0
PREFERRED SERVER=NETWARE1
(use the name of your Primary Server here)
SHOW DOTS=ON
ENTRY STACK SIZE=40
*****************************************************************
PRIMARY SERVER USER LOGIN SCRIPT
*****************************************************************
ATTACH NETWARE2/SUPERVISOR
MAP F:=NETWARE1/SYS:
MAP G:=NETWARE2/SYS:
MAP INS S4:=NETWARE1/SYS:/PUBLIC
MAP INS S5:=NETWARE2/SYS:/PUBLIC
*****************************************************************
SECONDARY SERVER USER LOGIN SCRIPT
*****************************************************************
MAP F:=NETWARE2/SYS:
MAP INS S4:=NETWARE2/SYS:/PUBLIC
Secondary Server login scripts are used only in the eventuality
that the Primary Server crashes and is unavailable for use for an
extended period. For more information, see "PREPARE FOR A CRASH!!!"
and "USER CONTROL" in the Manual (edition eight).
*****************************************************************
For this example, system login scripts are assumed to be blank.
*****************************************************************
NETWARE AND COMSPEC
*****************************************************************
If you have set COMPSPEC to find COMMAND.COM on a Netware volume,
e.g., COMSPEC=F:\COMMAND.COM, and that server goes down, Netware will
attempt to remap it to one of your local workstation drives, C: if you
have a hard disk, A: if you do not.
If you are using diskless workstations, this can be a problem. There are
three ways around this problem:
1. If you have an A: floppy drive, run with a disk in it which
contains COMMAND.COM.
2. If you have enough RAM, create a RAMdrive, D:, copy COMMAND.COM
to it and insert "SET COMSPEC=D:\COMMAND.COM" in your AUTOEXEC.BAT
or insert "COMSPEC D:\COMMAND.COM" in your login script.
3. Or, normally the best solution, insert "SET COMSPEC=\COMMAND.COM"
in your AUTOEXEC.BAT. This will cause COMMAND.COM to be loaded from
the root of whatever the current drive is. You will need a copy of
COMMAND.COM at the root of each of the drives you use, so it can
always be found. In the case of a diskless workstation mirroring
from F: to G:, place a copy of COMMAND.COM at the root of both
F: and G:. Setting the COMSPEC this way must be done in the
AUTOEXEC.BAT file or from the DOS command line. Netware will not let
you do it in the login script. To use this method, the user must have
proper access priveleges (Trustee Directory Rights) to the path where
COMMAND.COM is stored.
(C) 1989,90,91,92,93 NONSTOP NETWORKS LIMITED.